Skip to contentSkip to conversation

rsync: Security fixes from v3.4.1-sec-patches3

PATCH Yoann Congal 5 participants 10 messages Sep 17 – Oct 19 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 27 lines · Vijay Anusuri via lists.openembedded.org

Backport the security fixes from the upstream v3.4.1-sec-patches3 branch to address the known rsync security vulnerabilities.

The v3.4.1-sec-patches3 branch contains 239 commits. The GitHub workflow commits (037, 038, and 160), which only modify .github/workflows files, and the testsuite-only commits (238 and
239) are excluded because they are not applicable to the Yocto build.

The remaining 237 security fixes are combined into a single patch series and applied on top of the rsync 3.4.1 source.

SUSE has also backported these security fixes to rsync-3.4.1-160000.6.1 to address the corresponding CVEs.

References:

https://rsync.samba.org/security.html
https://github.com/RsyncProject/rsync/tree/v3.4.1-sec-patches3
https://bugzilla.suse.com/show_bug.cgi?id=CVE-2026-53802

This fix handles CVE-2025-10158 CVE-2026-29518 CVE-2026-43617 CVE-2026-43618 CVE-2026-43619 CVE-2026-43620 CVE-2026-45232 CVE-2026-44507 CVE-2026-44508 CVE-2026-44509 CVE-2026-44510 CVE-2026-53783 CVE-2026-53784 CVE-2026-53785 CVE-2026-53786 CVE-2026-53788 CVE-2026-53789 CVE-2026-53790 CVE-2026-53791 CVE-2026-53792 CVE-2026-53793 CVE-2026-53794 CVE-2026-53795 CVE-2026-53796 CVE-2026-53797 CVE-2026-53798 CVE-2026-53799 CVE-2026-53800 CVE-2026-53801 CVE-2026-53802 CVE-2026-53803 CVE-2026-70452 CVE-2026-70453 CVE-2026-70454 CVE-2026-70455 CVE-2026-70456 CVE-2026-70457 CVE-2026-70458 CVE-2026-70459 CVE-2026-70460 CVE-2026-70461 CVE-2026-70462 CVE-2026-70463 CVE-2026-70464

Dropped CVE-2025-10158.patch
Refreshed the patch 0001-Add-missing-prototypes-to-function-declarations.patch

Quoted 8 lines
---
 ...-prototypes-to-function-declarations.patch |    81 +-
 .../rsync/files/CVE-2025-10158.patch          |    36 -
 .../files/rsync-3.4.1-sec-patches3.patch      | 34052 ++++++++++++++++
 meta/recipes-devtools/rsync/rsync_3.4.1.bb    |     2 +-
 4 files changed, 34071 insertions(+), 100 deletions(-)
 delete mode 100644 meta/recipes-devtools/rsync/files/CVE-2025-10158.patch
 create mode 100644 meta/recipes-devtools/rsync/files/rsync-3.4.1-sec-patches3.patch

Hello,

I don't think I want to carry a 34000 lines patch.

Does the rsync project released a v3.4.1-sec-patches3 archive?

If not, can we try to switch the recipe to git and point SRCREV to the "rsync-3.4.1-sec-patches" branch?
Since the recipe is not git-based now, we'll need to switch to git first, then upgrade.

Regards,

Signature · 2 lines
Yoann Congal
Smile ECS
#2 lore raw
Quoted 39 lines · Yoann Congal
Quoted 27 lines · Vijay Anusuri via lists.openembedded.org

Backport the security fixes from the upstream v3.4.1-sec-patches3 branch to address the known rsync security vulnerabilities.

The v3.4.1-sec-patches3 branch contains 239 commits. The GitHub workflow commits (037, 038, and 160), which only modify .github/workflows files, and the testsuite-only commits (238 and
239) are excluded because they are not applicable to the Yocto build.

The remaining 237 security fixes are combined into a single patch series and applied on top of the rsync 3.4.1 source.

SUSE has also backported these security fixes to rsync-3.4.1-160000.6.1 to address the corresponding CVEs.

References:

https://rsync.samba.org/security.html
https://github.com/RsyncProject/rsync/tree/v3.4.1-sec-patches3
https://bugzilla.suse.com/show_bug.cgi?id=CVE-2026-53802

This fix handles CVE-2025-10158 CVE-2026-29518 CVE-2026-43617 CVE-2026-43618 CVE-2026-43619 CVE-2026-43620 CVE-2026-45232 CVE-2026-44507 CVE-2026-44508 CVE-2026-44509 CVE-2026-44510 CVE-2026-53783 CVE-2026-53784 CVE-2026-53785 CVE-2026-53786 CVE-2026-53788 CVE-2026-53789 CVE-2026-53790 CVE-2026-53791 CVE-2026-53792 CVE-2026-53793 CVE-2026-53794 CVE-2026-53795 CVE-2026-53796 CVE-2026-53797 CVE-2026-53798 CVE-2026-53799 CVE-2026-53800 CVE-2026-53801 CVE-2026-53802 CVE-2026-53803 CVE-2026-70452 CVE-2026-70453 CVE-2026-70454 CVE-2026-70455 CVE-2026-70456 CVE-2026-70457 CVE-2026-70458 CVE-2026-70459 CVE-2026-70460 CVE-2026-70461 CVE-2026-70462 CVE-2026-70463 CVE-2026-70464

Dropped CVE-2025-10158.patch
Refreshed the patch 0001-Add-missing-prototypes-to-function-declarations.patch

Quoted 8 lines
---
 ...-prototypes-to-function-declarations.patch |    81 +-
 .../rsync/files/CVE-2025-10158.patch          |    36 -
 .../files/rsync-3.4.1-sec-patches3.patch      | 34052 ++++++++++++++++
 meta/recipes-devtools/rsync/rsync_3.4.1.bb    |     2 +-
 4 files changed, 34071 insertions(+), 100 deletions(-)
 delete mode 100644 meta/recipes-devtools/rsync/files/CVE-2025-10158.patch
 create mode 100644 meta/recipes-devtools/rsync/files/rsync-3.4.1-sec-patches3.patch

Hello,

Quoted 8 lines

I don't think I want to carry a 34000 lines patch.

Does the rsync project released a v3.4.1-sec-patches3 archive?

If not, can we try to switch the recipe to git and point SRCREV to the "rsync-3.4.1-sec-patches" branch?
Since the recipe is not git-based now, we'll need to switch to git first, then upgrade.

Paul asked a good question about this idea though: How official is this branch?
Can you ask upstream the status of it? Will it stay published? Will we see v3.4.1-sec-patches4,5... branches someday?

Thanks!

Signature · 2 lines
Yoann Congal
Smile ECS
#3 lore raw
Quoted 49 lines · Yoann Congal
Quoted 39 lines · Yoann Congal
Quoted 27 lines · Vijay Anusuri via lists.openembedded.org

Backport the security fixes from the upstream v3.4.1-sec-patches3 branch to address the known rsync security vulnerabilities.

The v3.4.1-sec-patches3 branch contains 239 commits. The GitHub workflow commits (037, 038, and 160), which only modify .github/workflows files, and the testsuite-only commits (238 and
239) are excluded because they are not applicable to the Yocto build.

The remaining 237 security fixes are combined into a single patch series and applied on top of the rsync 3.4.1 source.

SUSE has also backported these security fixes to rsync-3.4.1-160000.6.1 to address the corresponding CVEs.

References:

https://rsync.samba.org/security.html
https://github.com/RsyncProject/rsync/tree/v3.4.1-sec-patches3
https://bugzilla.suse.com/show_bug.cgi?id=CVE-2026-53802

This fix handles CVE-2025-10158 CVE-2026-29518 CVE-2026-43617 CVE-2026-43618 CVE-2026-43619 CVE-2026-43620 CVE-2026-45232 CVE-2026-44507 CVE-2026-44508 CVE-2026-44509 CVE-2026-44510 CVE-2026-53783 CVE-2026-53784 CVE-2026-53785 CVE-2026-53786 CVE-2026-53788 CVE-2026-53789 CVE-2026-53790 CVE-2026-53791 CVE-2026-53792 CVE-2026-53793 CVE-2026-53794 CVE-2026-53795 CVE-2026-53796 CVE-2026-53797 CVE-2026-53798 CVE-2026-53799 CVE-2026-53800 CVE-2026-53801 CVE-2026-53802 CVE-2026-53803 CVE-2026-70452 CVE-2026-70453 CVE-2026-70454 CVE-2026-70455 CVE-2026-70456 CVE-2026-70457 CVE-2026-70458 CVE-2026-70459 CVE-2026-70460 CVE-2026-70461 CVE-2026-70462 CVE-2026-70463 CVE-2026-70464

Dropped CVE-2025-10158.patch
Refreshed the patch 0001-Add-missing-prototypes-to-function-declarations.patch

Quoted 8 lines
---
 ...-prototypes-to-function-declarations.patch |    81 +-
 .../rsync/files/CVE-2025-10158.patch          |    36 -
 .../files/rsync-3.4.1-sec-patches3.patch      | 34052 ++++++++++++++++
 meta/recipes-devtools/rsync/rsync_3.4.1.bb    |     2 +-
 4 files changed, 34071 insertions(+), 100 deletions(-)
 delete mode 100644 meta/recipes-devtools/rsync/files/CVE-2025-10158.patch
 create mode 100644 meta/recipes-devtools/rsync/files/rsync-3.4.1-sec-patches3.patch

Hello,

Quoted 8 lines

I don't think I want to carry a 34000 lines patch.

Does the rsync project released a v3.4.1-sec-patches3 archive?

If not, can we try to switch the recipe to git and point SRCREV to the "rsync-3.4.1-sec-patches" branch?
Since the recipe is not git-based now, we'll need to switch to git first, then upgrade.

Quoted 4 lines

Paul asked a good question about this idea though: How official is this branch?
Can you ask upstream the status of it? Will it stay published? Will we see v3.4.1-sec-patches4,5... branches someday?

Hi Yoann, Vijay,

Some thoughts here...

The upgrade to v3.4.3 was rejected [1] due to a few minor feature additions. In this case it may be lower risk to take an upgrade rather than backporting a 34 kLOC patch. I think we should avoid v3.5.0 due to the number of regressions reported [2]. v3.4.4 is an option. We can then see how many CVEs remain open and decide what to do about them.

The onus here is on contributors, not on Yoann as stable maintainer. To go ahead we would need some investigation, testing and a proposal to the TSC to approve the update as an exception to our usual stable policy.

[1]: https://lore.kernel.org/all/[email protected]/
[2]: https://github.com/RsyncProject/rsync/issues?q=is%3Aissue%20%223.5.0%22

Best regards,

Signature · 1 line
Paul Barker
#4 lore raw

Hi Yoann, Paul,

Thanks for the feedback.

I have opened a discussion [1] with the rsync upstream project to clarify the status and maintenance model of the v3.4.1-sec-patches3 and v3.2.7-sec-patches3 branches, including whether they will remain available and whether future security patch branches will be published.

Regarding the 3.4.4 upgrade, I noticed that upgrading from 3.4.1 to 3.4.4 would still leave us with around 33 CVEs to address. The rsync 3.5.0 release [2] addresses these 33 CVEs.

I will continue to investigate the available options

[1] https://github.com/RsyncProject/rsync/discussions/1095
[2] https://download.samba.org/pub/rsync/NEWS#3.5.0

Thanks & Regards,

Vijay

Quoted 94 lines · Paul Barker
Quoted 2 lines · Yoann Congal
Quoted 1 line · Yoann Congal

On Thu Sep 17, 2026 at 12:55 PM CEST, Vijay Anusuri via

Quoted 9 lines · lists.openembedded.org
Quoted 9 lines
Quoted 9 lines

Backport the security fixes from the upstream v3.4.1-sec-patches3 branch to address the known rsync security vulnerabilities.

The v3.4.1-sec-patches3 branch contains 239 commits. The GitHub workflow commits (037, 038, and 160), which only modify .github/workflows files, and the testsuite-only commits (238 and
239) are excluded because they are not applicable to the Yocto build.

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

The remaining 237 security fixes are combined into a single patch series and applied on top of the rsync 3.4.1 source.

SUSE has also backported these security fixes to

rsync-3.4.1-160000.6.1

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

to address the corresponding CVEs.

References:

https://rsync.samba.org/security.html
https://github.com/RsyncProject/rsync/tree/v3.4.1-sec-patches3
https://bugzilla.suse.com/show_bug.cgi?id=CVE-2026-53802

This fix handles CVE-2025-10158 CVE-2026-29518 CVE-2026-43617

CVE-2026-43618 CVE-2026-43619 CVE-2026-43620 CVE-2026-45232 CVE-2026-44507 CVE-2026-44508 CVE-2026-44509 CVE-2026-44510 CVE-2026-53783 CVE-2026-53784 CVE-2026-53785 CVE-2026-53786 CVE-2026-53788 CVE-2026-53789 CVE-2026-53790 CVE-2026-53791 CVE-2026-53792 CVE-2026-53793 CVE-2026-53794 CVE-2026-53795 CVE-2026-53796 CVE-2026-53797 CVE-2026-53798 CVE-2026-53799 CVE-2026-53800 CVE-2026-53801 CVE-2026-53802 CVE-2026-53803 CVE-2026-70452 CVE-2026-70453 CVE-2026-70454 CVE-2026-70455 CVE-2026-70456 CVE-2026-70457 CVE-2026-70458 CVE-2026-70459 CVE-2026-70460 CVE-2026-70461 CVE-2026-70462 CVE-2026-70463 CVE-2026-70464

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

Dropped CVE-2025-10158.patch
Refreshed the patch

0001-Add-missing-prototypes-to-function-declarations.patch

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
---
 ...-prototypes-to-function-declarations.patch |    81 +-
 .../rsync/files/CVE-2025-10158.patch          |    36 -
 .../files/rsync-3.4.1-sec-patches3.patch      | 34052

++++++++++++++++

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
 meta/recipes-devtools/rsync/rsync_3.4.1.bb    |     2 +-
 4 files changed, 34071 insertions(+), 100 deletions(-)
 delete mode 100644

meta/recipes-devtools/rsync/files/CVE-2025-10158.patch

Quoted 1 line
Quoted 1 line
Quoted 1 line
 create mode 100644

meta/recipes-devtools/rsync/files/rsync-3.4.1-sec-patches3.patch

Quoted 12 lines
Quoted 11 lines

Hello,

I don't think I want to carry a 34000 lines patch.

Does the rsync project released a v3.4.1-sec-patches3 archive?

If not, can we try to switch the recipe to git and point SRCREV to the "rsync-3.4.1-sec-patches" branch?
Since the recipe is not git-based now, we'll need to switch to git first, then upgrade.

Quoted 4 lines

Paul asked a good question about this idea though: How official is this branch?
Can you ask upstream the status of it? Will it stay published? Will we see v3.4.1-sec-patches4,5... branches someday?

Hi Yoann, Vijay,

Some thoughts here...

The upgrade to v3.4.3 was rejected [1] due to a few minor feature additions. In this case it may be lower risk to take an upgrade rather than backporting a 34 kLOC patch. I think we should avoid v3.5.0 due to the number of regressions reported [2]. v3.4.4 is an option. We can then see how many CVEs remain open and decide what to do about them.

The onus here is on contributors, not on Yoann as stable maintainer. To go ahead we would need some investigation, testing and a proposal to the TSC to approve the update as an exception to our usual stable policy.

[1]: https://lore.kernel.org/all/[email protected]/
[2]:
https://github.com/RsyncProject/rsync/issues?q=is%3Aissue%20%223.5.0%22

Best regards,

--
Paul Barker

#5 lore raw

Hi Yoann, Paul and Vijay,

v3.4.1-sec-patches3 and v3.2.7-sec-patches3 both the branches are part of official security release afaik.

these versions corresponds to ubuntu/launchpad PPA for racoon and noble respectively so i see them being maintained till 2031 and 2029 atleast(unless ubuntu decides on bumping those versions up in unforseen situations).

with that being said, yes it is trade-off between maintaining 34 kLOC patch and minor upgrade which we need to figure out.
upgrading to 3.4.4 is less favourable as it still leaves 33 CVE's open and for that we would still have a larger patch to maintain rather than patches getting applied directly.

Since rsync does not expose an architecture-wide library ( librsync is a completely distinct project), upgrading it will *never break the ABI of other compiled packages* in rootfs. No other binary links against rsync dynamically at the linker level. on top of it, rsync is maintaining backword compatability. So upgrading to 3.5.x wouldn't be an issue too.

To talk about the regressions in 3.5.0, they are being fixed in 3.5.1 which is planned to release on 21st september.

we have 2 ways in front of us:
1) maintain the 34 kLOC patch for 3.4.1.
Pros: we will mostly have maintainence till 2031( 1 year more than wrynose EOL).
cons: large patches to be maintained. (we can locally tar it though but still has to be maintained)

2) upgrade the 3.5.1
Pros: no need to maintain large patches and we would be in line with upstream.
Cons: we will be violating the stable upgrade policy of no new features and there are chances we would encounter same situation in future when more CVE's are found affecting the newer version.

i am fine with either of the way as one of fellow contributor. But, let me know your thoughts.

Regards,
Siddharth

#6 lore raw

Hi Yoann, Paul,

I checked with the rsync upstream maintainers regarding the security patch branches and the possibility of an archive/tarball.

They confirmed that v3.4.1-sec-patches3 and v3.2.7-sec-patches3 are official rsync security-maintenance branches. They have now also published:

- v3.4.1-sec-patches4
- v3.2.7-sec-patches4

These branches contain the security and compatibility fixes applicable to the respective older release lines after *-sec-patches3. Both branches have been tested against the refreshed stable testsuite.

Regarding the archive/tarball, the maintainer clarified that they do not plan to provide release tarballs for these security branches. The branches are intended to be used as reviewable Git sources from which downstream maintainers can cherry-pick commits or construct their own patch series.

Based on this, can we switch the rsync recipe to Git and use the v3.4.1-sec-patches4 & v3.2.7-sec-patches4 branches for Wrynose/Scarthgap?

This would allow us to consume the upstream security and compatibility fixes directly from the maintained security branch instead of carrying the large 34KLOC patch series.

The discussion with the rsync maintainers is here:
https://github.com/RsyncProject/rsync/discussions/1095

Thanks & Regards,
Vijay

Quoted 56 lines · Siddharth Doshi via lists.openembedded.org

Hi Yoann, Paul and Vijay,

v3.4.1-sec-patches3 and v3.2.7-sec-patches3 both the branches are part of official security release afaik.

these versions corresponds to ubuntu/launchpad PPA for racoon and noble respectively so i see them being maintained till 2031 and 2029 atleast(unless ubuntu decides on bumping those versions up in unforseen situations).

with that being said, yes it is trade-off between maintaining 34 kLOC patch and minor upgrade which we need to figure out.
upgrading to 3.4.4 is less favourable as it still leaves 33 CVE's open and for that we would still have a larger patch to maintain rather than patches getting applied directly.

Since rsync does not expose an architecture-wide library (librsync is a completely distinct project), upgrading it will *never break the ABI of other compiled packages* in rootfs. No other binary links against rsync dynamically at the linker level. on top of it, rsync is maintaining backword compatability. So upgrading to 3.5.x wouldn't be an issue too.

To talk about the regressions in 3.5.0, they are being fixed in 3.5.1 which is planned to release on 21st september.

we have 2 ways in front of us:
1) maintain the 34 kLOC patch for 3.4.1.
Pros: we will mostly have maintainence till 2031( 1 year more than wrynose EOL).
cons: large patches to be maintained. (we can locally tar it though but still has to be maintained)

2) upgrade the 3.5.1
Pros: no need to maintain large patches and we would be in line with upstream.
Cons: we will be violating the stable upgrade policy of no new features and there are chances we would encounter same situation in future when more CVE's are found affecting the newer version.

i am fine with either of the way as one of fellow contributor. But, let me know your thoughts.

Regards,
Siddharth

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#246070):
https://lists.openembedded.org/g/openembedded-core/message/246070
Mute This Topic: https://lists.openembedded.org/mt/121293944/7301997
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#7 lore raw
Quoted 23 lines · Vijay Anusuri

Hi Yoann, Paul,

I checked with the rsync upstream maintainers regarding the security patch branches and the possibility of an archive/tarball.

They confirmed that v3.4.1-sec-patches3 and v3.2.7-sec-patches3 are official rsync security-maintenance branches. They have now also published:

- v3.4.1-sec-patches4
- v3.2.7-sec-patches4

These branches contain the security and compatibility fixes applicable to the respective older release lines after *-sec-patches3. Both branches have been tested against the refreshed stable testsuite.

Regarding the archive/tarball, the maintainer clarified that they do not plan to provide release tarballs for these security branches. The branches are intended to be used as reviewable Git sources from which downstream maintainers can cherry-pick commits or construct their own patch series.

Based on this, can we switch the rsync recipe to Git and use the v3.4.1-sec-patches4 & v3.2.7-sec-patches4 branches for Wrynose/Scarthgap?

Quoted 7 lines

This would allow us to consume the upstream security and compatibility fixes directly from the maintained security branch instead of carrying the large 34KLOC patch series.

The discussion with the rsync maintainers is here:
https://github.com/RsyncProject/rsync/discussions/1095

Hi Vijay,

Thanks for checking with upstream. It seems a bit of a strange way of doing things to me - I am surprised these aren't further releases in the 3.4.x and 3.2.x series. Or at least they could be 3.4.1.x and 3.2.7.x releases. But if this is the way upstream want to handle things then that's their call.

We do need to discuss how this fits in with our policies on LTS maintenance. We will get back to you soon.

Best regards,

Signature · 1 line
Paul Barker
#8 lore raw
Quoted 47 lines · Paul Barker
Quoted 27 lines · Vijay Anusuri

Hi Yoann, Paul,

I checked with the rsync upstream maintainers regarding the security patch

branches and the possibility of an archive/tarball.

They confirmed that v3.4.1-sec-patches3 and v3.2.7-sec-patches3 are official rsync security-maintenance branches. They have now also published:

- v3.4.1-sec-patches4
- v3.2.7-sec-patches4

These branches contain the security and compatibility fixes applicable to the respective older release lines after *-sec-patches3. Both branches have
been tested against the refreshed stable testsuite.

Regarding the archive/tarball, the maintainer clarified that they do not plan to provide release tarballs for these security branches. The branches

are intended to be used as reviewable Git sources from which downstream maintainers can cherry-pick commits or construct their own patch series.

Based on this, can we switch the rsync recipe to Git and use the v3.4.1-sec-patches4 & v3.2.7-sec-patches4 branches for Wrynose/Scarthgap?

Quoted 8 lines

This would allow us to consume the upstream security and compatibility fixes directly from the maintained security branch instead of carrying the

large 34KLOC patch series.

The discussion with the rsync maintainers is here:
https://github.com/RsyncProject/rsync/discussions/1095

Hi Vijay,

Thanks for checking with upstream. It seems a bit of a strange way of doing things to me - I am surprised these aren't further releases in the 3.4.x and 3.2.x series. Or at least they could be 3.4.1.x and 3.2.7.x releases. But if this is the way upstream want to handle things then that's their call.

Quoted 7 lines

We do need to discuss how this fits in with our policies on LTS maintenance. We will get back to you soon.

Best regards,

--
Paul Barker

Hi Paul, Yoann,
Could you please share if there are any updates on this?

Regards,
Hetvi Thakar

#9 lore raw
Quoted 52 lines · On Thu, 2026-10-08 at 01:40 -0700, Hetvi Thakar -X (hthakar - E INFOCHIPS…
Quoted 50 lines · Paul Barker
Quoted 27 lines · Vijay Anusuri

Hi Yoann, Paul,

I checked with the rsync upstream maintainers regarding the security patch

branches and the possibility of an archive/tarball.

They confirmed that v3.4.1-sec-patches3 and v3.2.7-sec-patches3 are official rsync security-maintenance branches. They have now also published:

- v3.4.1-sec-patches4
- v3.2.7-sec-patches4

These branches contain the security and compatibility fixes applicable to the respective older release lines after *-sec-patches3. Both branches have
been tested against the refreshed stable testsuite.

Regarding the archive/tarball, the maintainer clarified that they do not plan to provide release tarballs for these security branches. The branches

are intended to be used as reviewable Git sources from which downstream maintainers can cherry-pick commits or construct their own patch series.

Based on this, can we switch the rsync recipe to Git and use the v3.4.1-sec-patches4 & v3.2.7-sec-patches4 branches for Wrynose/Scarthgap?

Quoted 8 lines

This would allow us to consume the upstream security and compatibility fixes directly from the maintained security branch instead of carrying the

large 34KLOC patch series.

The discussion with the rsync maintainers is here:
https://github.com/RsyncProject/rsync/discussions/1095

Hi Vijay,

Thanks for checking with upstream. It seems a bit of a strange way of doing things to me - I am surprised these aren't further releases in the 3.4.x and 3.2.x series. Or at least they could be 3.4.1.x and 3.2.7.x releases. But if this is the way upstream want to handle things then that's their call.

We do need to discuss how this fits in with our policies on LTS maintenance. We will get back to you soon.

Quoted 7 lines
Quoted 4 lines

Best regards,

--
Paul Barker

Hi Paul, Yoann,
Could you please share if there are any updates on this?

Apologies for the delays due to conference travel.

Debian have decided to upgrade to rsync 3.5.0 on their stable release series, with additional regression fixes backported from 3.5.1. There is an explanation in the Debian rsync NEWS file [1].

Based on this, Yoann and I think Yocto Project should do similar. This will need discussion with the TSC, probably next week. I'll follow up after that.

[1]: https://salsa.debian.org/debian/rsync/-/blob/debian/trixie/debian/rsync.NEWS

Thanks,

Signature · 1 line
Paul Barker
#10 lore raw
Quoted 68 lines · Paul Barker
Quoted 52 lines · On Thu, 2026-10-08 at 01:40 -0700, Hetvi Thakar -X (hthakar - E INFOCHIPS…
Quoted 50 lines · Paul Barker
Quoted 27 lines · Vijay Anusuri

Hi Yoann, Paul,

I checked with the rsync upstream maintainers regarding the security patch

branches and the possibility of an archive/tarball.

They confirmed that v3.4.1-sec-patches3 and v3.2.7-sec-patches3 are official rsync security-maintenance branches. They have now also published:

- v3.4.1-sec-patches4
- v3.2.7-sec-patches4

These branches contain the security and compatibility fixes applicable to the respective older release lines after *-sec-patches3. Both branches have
been tested against the refreshed stable testsuite.

Regarding the archive/tarball, the maintainer clarified that they do not plan to provide release tarballs for these security branches. The branches

are intended to be used as reviewable Git sources from which downstream maintainers can cherry-pick commits or construct their own patch series.

Based on this, can we switch the rsync recipe to Git and use the v3.4.1-sec-patches4 & v3.2.7-sec-patches4 branches for Wrynose/Scarthgap?

Quoted 8 lines

This would allow us to consume the upstream security and compatibility fixes directly from the maintained security branch instead of carrying the

large 34KLOC patch series.

The discussion with the rsync maintainers is here:
https://github.com/RsyncProject/rsync/discussions/1095

Hi Vijay,

Thanks for checking with upstream. It seems a bit of a strange way of doing things to me - I am surprised these aren't further releases in the 3.4.x and 3.2.x series. Or at least they could be 3.4.1.x and 3.2.7.x releases. But if this is the way upstream want to handle things then that's their call.

We do need to discuss how this fits in with our policies on LTS maintenance. We will get back to you soon.

Quoted 7 lines
Quoted 4 lines

Best regards,

--
Paul Barker

Hi Paul, Yoann,
Could you please share if there are any updates on this?

Apologies for the delays due to conference travel.

Debian have decided to upgrade to rsync 3.5.0 on their stable release series, with additional regression fixes backported from 3.5.1. There is an explanation in the Debian rsync NEWS file [1].

Quoted 5 lines

Based on this, Yoann and I think Yocto Project should do similar. This will need discussion with the TSC, probably next week. I'll follow up after that.

[1]: https://salsa.debian.org/debian/rsync/-/blob/debian/trixie/debian/rsync.NEWS

Hi,

The TSC has discussed the state of rsync on wrynose/scarthgap. It's a difficult situation, on one hand we have a set of backported CVE patches which are large, complex and impossible to review & maintain effectively. On the other hand we have a new rsync release which had known regressions and is definitely not a risk-free upgrade.

The TSC has concluded that taking the upgrade is preferable here. Neither myself or the TSC are particularly happy about that, but it's the least-worst option on the table. It does not mean that the stable branch rules are being relaxed in general, the preference continues to be for backporting individual CVE fixes or following a trusted upstream stable branch which aligns with our stable branch policies. It just means that in this individual case, the TSC thinks the risks of taking the rsync upgrade are outweighed by the risks of carrying patches totaling over 34 kLOC or leaving the CVEs unpatched.

Please submit patches to upgrade rsync on both wrynose and scarthgap. I would suggest upgrading to v3.5.1 to align with what we currently have on master and blacksail and to ensure that we have the fixes for the regressions introduced in v3.5.0.

Best regards,

Signature · 1 line
Paul Barker